Risk Mitigation Techniques in Agile Development Processes

The main purpose of agile development methods is to reduce risks leading to a more successful and effective information system. In fact, analysing priorities, finding and identifying risks are important activities in all development approaches, including Agile development. However, some studies seek to assess risk management based on agile global software development (GSD) and provide mitigation measures to address specific risks. The risk mitigation technique for good development for sustainable development is expected to be designed to achieve time efficiency improvements to obtain greater resources at lower cost and thereby gain and maintain a competitive advantage

Risk Mitigation Techniques in Agile Development Processes

The main purpose of agile development methods is to reduce risks leading to a more successful and effective information system. In fact, analysing priorities, finding and identifying risks are important activities in all development approaches, including Agile development. However, some studies seek to assess risk management based on agile global software development (GSD) and provide mitigation measures to address specific risks. The risk mitigation technique for good development for sustainable development is expected to be designed to achieve time efficiency improvements to obtain greater resources at lower cost and thereby gain and maintain a competitive advantage

Non-Functional Requirement Traceability Process Model for Agile Software Development

Agile methodologies have been appreciated for the fast delivery of software. They are criticized for poor handling of Non-Functional Requirements (NFRs) such as security and performance and difficulty in tracing the changes caused by updates in NFR that are also associated with Functional Requirements (FRs).This paper presents a novel approach named Traceability process model of Agile Software Development for Tracing NFR change impact (TANC). In order to validate TANC’s compatibility with most of Agile process models, we present a logical model that synchronizes TANC with the two of enhanced models: secure feature-driven development (SFDD) and secured scrum (SScrum).Then, we conducted a case study on TANC using a tool support called Sagile. In terms of adaptability with agile process model, the logical model could be depicted in SFDD and the case study proved that TANC is carried out successfully in SFDD

Fuzzy C-mean missing data imputation for analogy-based effort estimation

The accuracy of effort estimation in one of the major factors in the success or failure of software projects. Analogy-Based Estimation (ABE) is a widely accepted estimation model since its flow human nature in selecting analogies similar in nature to the target project. The accuracy of prediction in ABE model in strongly associated with the quality of the dataset since it depends on previous completed projects for estimation. Missing Data (MD) is one of major challenges in software engineering datasets. Several missing data imputation techniques have been investigated by researchers in ABE model. Identification of the most similar donor values from the completed software projects dataset for imputation is a challenging issue in existing missing data techniques adopted for ABE model. In this study, Fuzzy C-Mean Imputation (FCMI), Mean Imputation (MI) and K-Nearest Neighbor Imputation (KNNI) are investigated to impute missing values in Desharnais dataset under different missing data percentages (Desh-Miss1, Desh-Miss2) for ABE model. FCMI-ABE technique is proposed in this study. Evaluation comparison among MI, KNNI, and (ABE-FCMI) is conducted for ABE model to identify the suitable MD imputation method. The results suggest that the use of (ABE-FCMI), rather than MI and KNNI, imputes more reliable values to incomplete software projects in the missing datasets. It was also found that the proposed imputation method significantly improves software development effort prediction of ABE model

Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development

Currently, it is crucial to develop a complex software on time. Agile software development methodologies provide methods to develop a system in term of time and cost-saving but it has been criticized for software quality management. In this paper, a case study is used to find out the need of NFR change impact traceability approach in most of Agile software methodology. This case study was conducted in an undergraduate course that trained the students on how to develop software using Agile process model.This case study has been conducted for 4 months in an undergraduate-level course, Application Development. The samples of this case study are among Year 3 undergraduate students. The case study shows the lack of traceability techniques in the existing Agile process model (SFDD- Secured Feature Driven Development) that result to non-awareness of NFR change impact during development. Based on the case study mentioned the main objective of the case study conducted in survey is to empirically test the theoretical constructs and the hypothesized relationships of the research issues that concern on the lack of change impact management towards NFR in Agile Software Methodology.  TANC (Traceability for Agile Non-Functional Requirement Change Impact) model offered techniques in tracing change impact during the agile development process. Therefore, the result of the case study, a traceability process model needs to design in order to tackle the NFR change impact issues in Agile software development

Case study on non-functional requirement change impact traceability for agile software development

Currently, it is crucial to develop a complex software on time. Agile software development methodologies provide methods to develop a system in term of time and cost-saving but it has been criticized for software quality management. In this paper, a case study is used to find out the need of NFR change impact traceability approach in most of Agile software methodology. This case study was conducted in an undergraduate course that trained the students on how to develop software using Agile process model. This case study has been conducted for 4 months in an undergraduate-level course, Application Development. The samples of this case study are among Year 3 undergraduate students. The case study shows the lack of traceability techniques in the existing Agile process model (SFDD-Secured Feature Driven Development) that result to non-awareness of NFR change impact during development. Based on the case study mentioned the main objective of the case study conducted in survey is to empirically test the theoretical constructs and the hypothesized relationships of the research issues that concern on the lack of change impact management towards NFR in Agile Software Methodology. TANC (Traceability for Agile Non-Functional Requirement Change Impact) model offered techniques in tracing change impact during the agile development process. Therefore, the result of the case study, a traceability process model needs to design in order to tackle the NFR change impact issues in Agile software development

Malware awareness tool for internet safety using gamification techniques

Malwares are detrimental to those who are ignorant of their existence. However, the adverse effects of malwares can be easily avoided by being aware of Internet safety. In this paper, a malware awareness tool targeted for university students was developed. The Game Development Lifecycle (GDLC) model was applied in developing this tool. The tool development phase began with initiation, then pre-production, production, testing, beta testing, and ended with the release phase. Once the malware awareness tool was developed, functionality tests and awareness level tests were conducted on university students to ensure the tool is fully operative. Through the tests, it was shown that this tool was received with positive responses from its target users. As for the awareness level test, a majority of 15 students were aware of the purpose of the gamification in the malware awareness tool. In a nutshell, the malware awareness tool that was developed raised university student's consciousness on malwares and increased their awareness level pertaining to Internet threats

Intelligent bothouse: trend of development of industry 4.0

The purpose of this paper is to accommodate the current trend of focusing on the development of Industry 4.0. This is by making a computer, a computer-controlled robot or a software thinks intelligently, in the similar manner the intelligent human thinks. Also, the project is designed to correct problem regarding the incremental total number of house breaks ins. This project is conducted through a series of phases within Evolutionary Prototyping software process. In this paper, intelli-gent-BotHouse system is a minor invention to overlap with Industry 4.0 which is an automated industry. The intelligent-BotHouse system is a smart security house system which allows house member to manage, control and monitor a home environment. First and foremost, this system allows house members to access the system through three main interfaces namely, the physical intact, the mobile platform or the web page provided the given inputs are the correct security re-quirements. The house members can then control the house appliances, house security features and safety monitoring sensors without any location constraints. As a result, house members are able to connect to their house even if they are far away. Eventually, the house members are alerted with the hazards, the threats and the information inside of a house. At the end, the probability of burglary crime, lost of valuable property, hazard, accident or any in-house harmful scenario is minimized. Ease of managing house environment with the pre-set wireless connection can be executed using only a mobile Android smartphone or a computer-based device

Measuring risk mitigation techniques in agile global software development

The main purpose of an Agile development method is to reduce risks, leading to a more successful and effective information system as it had overcome limitations faced in a traditional software development method. This reason lead many to adopt the Agile methodology, especially for global software development (GSD) projects. However, most are not aware of the risks introduced when using agile methods in GSD projects. The risks in GSD projects are dynamic due to factor multiplicity (e.g., multi-locations, multi-groups, multi-cultures, multi-technologies, and multi-standards). This study aims to distinguish the difference between two risk mitigation techniques as an overall technique in tackling the same issue, which is communication issues introduced by the geographical distance between two development teams

Systematic literature review on global software development risks in agile methodology

Background: The word 'Global Software Development' can be described as the development of software, with development teams spread across different geographical locations. Problem statement: The issues arise when there are gaps in information, workflows or processes, policies and others in the world. Objective: This paper aims to build an understanding of the risk in Global Software Development. Then, to identify category risk in Global Software Development and how Agile can reduce or mitigate their challenges. Method: This review paper using the standard systematic literature review method by Kitchehamm by reviewing and analyzing the relevant state-of -art techniques and approaches in the journal libraries based on the research questions. Results: The findings show that communication in Agile Global Software development is the main risk challenge. Contribution: The contributions of this paper may support the academician to propose and validate an enhanced approach to solve the issues if risk management in Agile GSD environment and assist the practitioners in choosing the most suitable and relevant method based on the requirement of Agile GSD project. This review paper is also focusing on the contribution to the Software Engineering Management and Software Engineering Models and Methods Knowledge Area